Selectively uploading applications to a mobile device based on power consumption

ABSTRACT

A computer-implemented method, system, and/or computer program product controls downloading of an application to a mobile device based on power consumption of the application. A server receives a first power nameplate for a first application and a second power nameplate for a second application, a first priority rating of the first application and a second priority rating of the second application, a power descriptor that identifies an amount of power available to a mobile device, and a set of application downloading rules. The set of application downloading rules includes a soft rule, a hard rule, and a medium rule. The server then selectively uploads, to the mobile device, the first application or the second application based on a selected rule.

BACKGROUND

The present disclosure relates to the field of computing devices, andspecifically to the field of mobile computing devices that are batterypowered. Still more specifically, the present disclosure relates to thefield of managing power consumption by applications that are loaded ontothe mobile computing devices.

SUMMARY

A computer-implemented method, system, and/or computer program productcontrols downloading of an application to a mobile device based on powerconsumption of the application. A server receives a first powernameplate for a first application and a second power nameplate for asecond application. The first power nameplate identifies a first powerconsumption level requirement of the first application, the secondpower-identifies a second power consumption level requirement of thesecond application, and the second power consumption level requirementis a lower power consumption level requirement than the first powerconsumption level requirement. The server receives a first priorityrating of the first application and a second priority rating of thesecond application, where the first priority rating is a higher priorityrating than the second priority rating. The server receives a powerdescriptor, from a mobile device, which identifies an amount of poweravailable to the mobile device from a battery on the mobile device. Theserver receives a set of application downloading rules from the mobiledevice. The set of application downloading rules includes a soft rule, ahard rule, and a medium rule. The soft rule prioritizes downloading thefirst application over the second application based on the higherpriority rating of the first application regardless of the higher powerconsumption level requirement of the first application. The hard ruleprioritizes downloading the second application over the firstapplication based on the lower power consumption level requirement ofthe second application regardless of the higher priority rating of thefirst application. The medium rule prioritizes downloading the secondapplication over the first application in response to the amount ofpower available to the mobile device from the battery being below apredetermined value. The server receives a request from the mobiledevice to download the first application and the second application, aswell as a rule selection message from the mobile device, whichselectively chooses a selected rule from the soft rule, the hard rule,and the medium rule. The server then selectively uploads, to the mobiledevice, the first application or the second application based on theselected rule from the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an exemplary system and network in which the presentdisclosure may be implemented;

FIG. 2 illustrates a hashing of values represented by a set ofvisually-coded power nameplates in accordance with one or moreembodiments of the present invention;

FIG. 3 depicts a relationship between a mobile device and a server inaccordance with one or more embodiments of the present invention; and

FIG. 4 is a high-level flow chart of one or more steps performed by oneor more processors and/or other hardware to control downloading of anapplication to a mobile device based on power consumption of theapplication.

DETAILED DESCRIPTION

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

With reference now to the figures, and in particular to FIG. 1, there isdepicted a block diagram of an exemplary system and network that may beutilized by and/or in the implementation of the present invention. Someor all of the exemplary architecture, including both depicted hardwareand software, shown for and within computer 101 may be utilized bysoftware deploying server 149 and/or mobile device 123 shown in FIG. 1,and/or mobile device 223 depicted in FIG. 2, and/or mobile device 323and/or server 301 shown in FIG. 3.

Exemplary computer 101 includes a processor 103 that is coupled to asystem bus 105. Processor 103 may utilize one or more processors, eachof which has one or more processor cores. A video adapter 107, whichdrives/supports a display 109, is also coupled to system bus 105. Systembus 105 is coupled via a bus bridge 111 to an input/output (I/O) bus113. An I/O interface 115 is coupled to I/O bus 113. I/O interface 115affords communication with various I/O devices, including a keyboard117, a mouse 119, and/or a media tray 121 (which may include storagedevices such as CD-ROM drives, multi-media interfaces, etc.). While theformat of the ports connected to I/O interface 115 may be any known tothose skilled in the art of computer architecture, in one embodimentsome or all of these ports are universal serial bus (USB) ports.

As depicted, computer 101 is able to communicate with a softwaredeploying server 149 and/or other devices/systems using a networkinterface 129 to a network 127. Network interface 129 is a hardwarenetwork interface, such as a network interface card (NIC), etc. Network127 may be an external network such as the Internet, or an internalnetwork such as an Ethernet or a virtual private network (VPN). In oneor more embodiments, network 127 is a wireless network, such as a Wi-Finetwork, a cellular network, etc. Network 127 may connect computer 101to a mobile device 123 (e.g., a smart phone, a tablet computer, a laptopcomputer, or other electronic device that is battery operated) and/or asoftware deploying server 149.

A hard drive interface 131 is also coupled to system bus 105. Hard driveinterface 131 interfaces with a hard drive 133. In one embodiment, harddrive 133 populates a system memory 135, which is also coupled to systembus 105. System memory is defined as a lowest level of volatile memoryin computer 101. This volatile memory includes additional higher levelsof volatile memory (not shown), including, but not limited to, cachememory, registers and buffers. Data that populates system memory 135includes computer 101's operating system (OS) 137 and applicationprograms 143.

OS 137 includes a shell 139, for providing transparent user access toresources such as application programs 143. Generally, shell 139 is aprogram that provides an interpreter and an interface between the userand the operating system. More specifically, shell 139 executes commandsthat are entered into a command line user interface or from a file.Thus, shell 139, also called a command processor, is generally thehighest level of the operating system software hierarchy and serves as acommand interpreter. The shell provides a system prompt, interpretscommands entered by keyboard, mouse, or other user input media, andsends the interpreted command(s) to the appropriate lower levels of theoperating system (e.g., a kernel 141) for processing. While shell 139 isa text-based, line-oriented user interface, the present invention willequally well support other user interface modes, such as graphical,voice, gestural, etc.

As depicted, OS 137 also includes kernel 141, which includes lowerlevels of functionality for OS 137, including providing essentialservices required by other parts of OS 137 and application programs 143,including memory management, process and task management, diskmanagement, and mouse and keyboard management.

Application programs 143 include a renderer, shown in exemplary manneras a browser 145. Browser 145 includes program modules and instructionsenabling a world wide web (WWW) client (i.e., computer 101) to send andreceive network messages to the Internet using hypertext transferprotocol (HTTP) messaging, thus enabling communication with softwaredeploying server 149 and other systems.

Application programs 143 in computer 101's system memory (as well assoftware deploying server 149's system memory) also include Logic forControlling Application Uploads to Mobile Devices (LCAUMD) 147. LCAUMD147 includes code for implementing the processes described below,including those described in FIGS. 2-4.

Also within computer 101 is a power source 125. When plugged into anearly unlimited power supply (e.g., a power grid from a power company),the power source 125 is the system of outlets, wires, transformers thatsupport the power grid. However, when part of a mobile computing devicesuch as mobile device 123, power source 125 is a battery.

The hardware elements depicted in computer 101 are not intended to beexhaustive, but rather are representative to highlight essentialcomponents required by the present invention. For instance, computer 101may include alternate memory storage devices such as magnetic cassettes,digital versatile disks (DVDs), Bernoulli cartridges, and the like.These and other variations are intended to be within the spirit andscope of the present invention.

With reference now to FIG. 2, a hashing of values represented by a setof visually-coded power nameplates in accordance with one or moreembodiments of the present invention is presented.

Assume that multiple applications 1-4 are running on mobile device 223(analogous to mobile device 123 shown in FIG. 1). Each of theapplications 1-4 consumes power from a battery (e.g., power source 125shown in FIG. 1). The amount of power consumed by each of theapplications 1-4 is represented by a corresponding power nameplate 202a-202 d. Each of the power nameplates 202 a-202 d represent an amount ofpower that a mobile application can consume during peak usage. Thus, theamount of power used/shared is based on (1) the particular mobileapplications, and (2) the name plate power (i.e. maximum power) consumedby the mobile applications.

As shown for explanatory purposes, application 1 consumes 2.7 Watts ofpower from the battery; application 2 consumes 2.3 Watts of power fromthe battery; application 3 consumes 1.4 Watts of power from the battery;and application 4 consumes 0.7 Watts of power from the battery. Sincemany batteries in mobile devices such as a smart phone only can store5.0 Wh, running all of the applications 1-4 will fully deplete thebattery in mobile device 223 in much less than one hour (e.g.,approximately 40 minutes).

However, not all of the applications 1-4 may be running at all times. Assuch, a hash map 204 is generated. Hash map 204 is a calculation of thetotal amount of power consumed by applications 1-4 during somepredefined period of time. Thus, assuming that all of the applications1-4 are running simultaneously, then in 40 minutes they will use 5.0 Wh,and the battery will be depleted.

However, different applications from applications 1-4 may be turned onand off during some predefined period of time. For example, assume thatthe predefined period of time (for which power consumption will becalculated to create the hash map 204) is four hours. Assume furtherthat application 1 only runs for 30 minutes during those four hours (andthus uses 1.35 Wh of power); application 2 only runs for 10 minutesduring those four hours (and thus uses 0.4 Wh of power); application 3only runs for 30 minutes during those four hours (and thus uses 0.7 Whof power); and application 4 only runs for 2 hours during those fourhours (and thus uses 1.4 Wh of power). As such, the total amount ofpower used by these four applications during the predefined period oftime (hour hours) by applications 1-4 is 3.85 Wh (1.35+0.4+0.7+1.4=3.85Wh).

Alternatively, the hash map 204 is just a peak power draw for the mobiledevice 223. That is, an energy monitor continuously monitors how muchpower is being consumed at any point in time. When a new peak in powerconsumption occurs, then the hash map 204 is updated (and stored in anoffline cache 303 depicted in FIG. 3). For example, if mobile device 223has a spike in power usage of 4.7 Watts, then 4.7 W is stored in theoffline cache 303 in FIG. 3. However, if mobile device 223 later has aspike in power user of 5.3 Watts, then 5.3 W replaces the 4.7 W storedin offline cache 303.

In a preferred embodiment, hash map 204 is created within mobile device223.

As shown in FIG. 2, mobile device 223 has a battery 225, which is anytype of power storage device capable of storing electrical energy.

With reference now to FIG. 3, a relationship between a mobile device anda server in accordance with one or more embodiments of the presentinvention is represented.

As shown in FIG. 3, the hash map 204 discussed above from FIG. 2 isstored in an offline cache 303 within a mobile device 323 (analogous tomobile device 123 shown in FIG. 1 and mobile device 223 shown in FIG.2). In order to conserve energy, the hash 204 is only createdperiodically (e.g., during certain non-contiguous periods of time) andthen stored in an offline cache 303 (e.g., a non-volatile memory thatdoes not draw power from the battery in the mobile device 323).

A user may wish to download an application onto the mobile device 323.This desire of the user is understood by mobile device 323 as an inputfrom the user to a input device on the mobile. For example, the user mayclick a “Download now” button on a website that would download anapplication onto the mobile device 323.

Alternatively, logic within the mobile device 323 may autonomouslyrequest that an application be downloaded onto the mobile device 323.For example, one program (e.g., a graphics program) may need an audioprogram (e.g., an audio driver) to operate. If the audio driver is notinstalled on the mobile device 323, then the graphics program mayautomatically request that the audio driver be installed onto the mobiledevice 323.

Rather than directly performing such a download, however, an applicationdownload alert monitor 305 will request that an energy managementservice 307, which resides in a server 301 (analogous to computer 101shown in FIG. 1), grant permission for and implement the uploading ofthe requested application to the mobile device 323.

As such, the application download alert monitor 305 sends to the energymanagement service 307 (1) an identifier of the requested/desiredapplication; (2) that application's power nameplate (e.g., 2.7 Watts forapplication 1, as identified by power nameplate 202 a); and (3) a hashfrom hash map 204 (i.e., a power-describing hash pulled from offlinecache 303 for a predefined period of time in the past). This informationis stored in the server store 311.

Note that hash map 204 shows the amount of power consumed by runningapplications on mobile device 323 during certain time periods. Forexample, one of the hashes stored in offline cache 303 may represent theamount of time used at night, while another of the hashes stored in theoffline cache 303 may be for weekdays between 8:00 AM-9:00 AM. Thus, inone embodiment, the application download alert monitor 305 may also sentthe energy management service 307 the specific hash of power consumptionfor a time period that the requested new application will be used.

As shown in FIG. 3, the energy management service 307 then alerts analert service 309 of the request from mobile device 323 to download thenew application, along with the (1) identifier of the requested/desiredapplication, (2) the application's power nameplate, and (3) a hash fromhash map 204. Alert service 309 then takes appropriate action, such asallowing the new application to be downloaded to the mobile device 323,blocking the new application from being downloaded to the mobile device323, removing one or more applications from the mobile device in orderto free up power needed by the new application, turning off (e.g.,disabling) one or more applications from the mobile device in order tofree up power needed by the new application, etc.

With reference now to FIG. 4, a high-level flow chart of one or moresteps performed by one or more processors and/or other hardware tocontrol downloading of an application to a mobile device based on powerconsumption of the application is presented.

After initiator block 402, a server (e.g., server 101 shown in FIG. 1,depicted as server 301 in FIG. 3) receives a first power nameplate(e.g., power nameplate 202 a shown in FIG. 2) for a first application(e.g., application 1) and a second power nameplate (e.g., powernameplate 202 b) for a second application (e.g., application 2), asdescribed in block 404.

As described herein, the first power nameplate (which may be color-codedor otherwise visually coded) identifies a first power consumption levelrequirement of the first application (e.g., 2.7 W). The second powernameplate identifies a second power consumption level requirement of thesecond application (e.g., 2.3 W). As shown in FIG. 2, the second powerconsumption level requirement is a lower power consumption levelrequirement (2.3 W) than the first power consumption level requirement(2.7 W).

As described in block 406 in FIG. 4, the server also receives a firstpriority rating of the first application and a second priority rating ofthe second application, where the first priority rating is a higherpriority rating than the second priority rating. For example, assumethat the mobile device monitors a patient in a hospital, thatapplication 1 shown in FIG. 1 has been predetermined to be missioncritical (e.g., application 1 controls a life-support system for thepatient), and that application 2 has been predetermined to be less thanmission critical (e.g., application 2 merely monitors a room temperatureof a room in which the patient is located). As such, application 1 has ahigher priority rating than application 2.

As described in block 408, the server receives a power descriptor fromthe mobile device. The power descriptor identifies an amount of poweravailable to the mobile device from a battery on the mobile device. Forexample, assume that mobile device 223 has a battery (depicted in FIG. 2as battery 225). The power descriptor may be (1) a maximum power ratingfor the battery 225 (e.g., 5.0 Wh), and/or (2) a current amount of poweravailable from battery 225 (e.g., 3.0 Wh, assuming that 2.0 Wh havealready been drawn from battery 225).

As described in block 410, the server receives a set of applicationdownloading rules. The set of application downloading rules includes asoft rule, a hard rule, and a medium rule.

The soft rule is defined as a rule that prioritizes downloading thefirst application over the second application based on the higherpriority rating of the first application regardless of the higher powerconsumption level requirement of the first application. That is, ifapplication 1 in FIG. 2 has a higher priority than application 2, thenapplication 1 is allowed to be uploaded to the mobile device 223, eventhough it draws more power (2.7 W) than application 2 (2.3 W).

The hard rule is defined as a rule that prioritizes downloading thesecond application over the first application based on the lower powerconsumption level requirement of the second application regardless ofthe higher priority rating of the first application. That is, eventhough application 1 has a higher priority than application 2, thefactor that application 1 consumes more power than application 2 isenough to cause the upload of application 2 before (and/or in lieu of)uploading application 1 to the mobile device 223.

The medium rule is defined as a rule that prioritizes downloading thesecond application over the first application in response to the amountof power available to the mobile device from the battery being below apredetermined value. For example, if only 2.5 Wh of energy are availablefrom the battery 225 in mobile device 223, and an assumption is madethat either application 1 or application 2 will be running for one hour,then application 2 will be uploaded to the mobile device 223, since itonly requires 2.3 Wh of energy, which the battery 225 is able toprovide. (Application 1 is not uploaded to mobile device 223, sincebattery 225 is not able to provide the needed 2.7 Wh of energy needed byapplication 1.)

As described in block 412, the server receives a request to upload thefirst application and the second application to the mobile device (e.g.,mobile device 123 shown in FIG. 1, also depicted in FIG. 3 as mobiledevice 323). As described in block 414, the server also receives a ruleselection message, which chooses a selected rule from the soft rule, thehard rule, and the medium rule. That is, the energy management service307 (e.g., part of LCAUMD 147 shown in FIG. 1) and/or the mobile client323 shown in FIG. 3 provide the server 301 with the rule selectionmessage, directing the server 301 to obey/follow either the soft rule,the hard rule, or the medium rule described above.

As described in block 414, the server then selectively uploads, to themobile device, the first application or the second application based onthe selected rule, as described above.

The flow-chart from FIG. 4 ends at terminator block 418.

In an embodiment of the present invention, the server receives, from theenergy management service 307 and/or the mobile device 323 shown in FIG.3, a usage message. The usage message describes a prediction of anamount of time during a predefined time period that the mobile devicewill be running the first application. For example, application 1 shownin FIG. 2 may only be expected to run for only 10 minutes (“a predictionof an amount of time”) during the present week (“a predefined timeperiod”). This prediction may be based on analytics that describe howlong and/or frequently application 1 is called upon to run based onother applications running within mobile device 223, the architecture ofmobile device 223, etc.

The server then compares the amount of time during the predefined timeperiod that the mobile device will be running the first application to apredetermined limit of time. In response to determining that the amountof time during the predefined time period that the mobile device will berunning the first application is less than the predetermined limit oftime, the server disregards the hard rule and uploads the firstapplication to the mobile device. That is, even though application 2uses less power than application 1, the hard rule (which requiresapplications that use less power to be uploaded before applications thatuse more power) is ignored, since the mobile device 223 has enough powerto handle application 1 for the short amount of time that application 1will be running (“less than the predetermined limit of time”).

In one embodiment of the present invention, the server samples anaverage energy consumption by the mobile device for a predeterminedsampling time interval (e.g., hash map 204 shown in FIG. 2). The serverthus selects one of the hard rule, soft rule, and medium rule based onthe average energy consumption by the mobile device for thepredetermined sampling time interval. That is, an average amount ofpower consumed over time (rather than a maximum potential powerconsumption) determines which rule is applied. For example, even thoughapplications 1-4 shown in FIG. 2 can possibly draw 7.1 Watts in an hour,if they run only intermittently (e.g., resulting in the “average energyconsumption by the mobile device for a predetermined sampling timeinterval” that is only 2.0 Watts per hour), then the hard rule thatwould evict (or else prevent the uploading of) application 1 would notbe relevant.

In an embodiment of the present invention, the selected rule is selectedbased on a priority level difference between the first priority ratingand the second priority rating. That is, if the soft rule is applied,then the application with the higher priority (e.g., application 1) isselected over the application with the lower priority (e.g., application2) only if there is enough of a difference between their prioritylevels. For example, assume that application 1 has been assigned apriority level of 1, and application 2 has been assigned a prioritylevel of 2. As such, there is little difference in their prioritylevels, and there is little motivation to apply the soft rule (in whichhigher priority applications are uploaded before or instead of lowerpriority applications). As such, the hard rule will be selected andapplied, and the application with the lower energy consumption (e.g.,application 2) is selected over the application with the higher energyconsumption (e.g., application 1).

However, if application 1 still has the priority level of 1, butapplication 2 now has the priority level of 10 (e.g., on a scale of1-10, with 1 being the highest priority and 10 being the lowestpriority), then there is great motivation to upload application 1 beforeor instead of application 2, since application 1 is so much moreimportant than application 2. Thus, in this scenario, the soft rule willbe selected and applied, and the application with the higher priority(e.g., application 1) is selected over the application with the lowerpriority (e.g., application 2).

In an embodiment of the present invention, assume that the firstapplication has been uploaded to the mobile device. In this embodiment,the server determines that usage of the first application on the mobiledevice exceeds a predetermined value, and directs the mobile device toremove the first application from the mobile device. The server thenuploads the second application to the mobile device. That is, ifuploading application 1 (which uses a high level of power) overwhelmsthe battery 225 in FIG. 2, the application 1 is then removed from themobile device 223, and is replaced with application 2, which uses lesspower.

In an embodiment of the present invention, assume that the serverdetermines that the mobile device does not have sufficient battery powerto operate a new application (e.g., application 1). If so, then theserver deletes other applications that are already running on the mobiledevice, in order to free up enough power to run application 1.

Similarly, in one embodiment of the present invention, if a particularapplication that has been previously uploaded to the mobile device 223has not run in more than a predefined amount of time (e.g., a particularapplication has not been called on to run within mobile device 223 inover a month), then that application is automatically purged (deleted)from the mobile device 223.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of various embodiments of the present invention has beenpresented for purposes of illustration and description, but is notintended to be exhaustive or limited to the present invention in theform disclosed. Many modifications and variations will be apparent tothose of ordinary skill in the art without departing from the scope andspirit of the present invention. The embodiment was chosen and describedin order to best explain the principles of the present invention and thepractical application, and to enable others of ordinary skill in the artto understand the present invention for various embodiments with variousmodifications as are suited to the particular use contemplated.

Any methods described in the present disclosure may be implementedthrough the use of a VHDL (VHSIC Hardware Description Language) programand a VHDL chip. VHDL is an exemplary design-entry language for FieldProgrammable Gate Arrays (FPGAs), Application Specific IntegratedCircuits (ASICs), and other similar electronic devices. Thus, anysoftware-implemented method described herein may be emulated by ahardware-based VHDL program, which is then applied to a VHDL chip, suchas a FPGA.

Having thus described embodiments of the present invention of thepresent application in detail and by reference to illustrativeembodiments thereof, it will be apparent that modifications andvariations are possible without departing from the scope of the presentinvention defined in the appended claims.

What is claimed is:
 1. A computer-implemented method to controldownloading of an application to a mobile device based on powerconsumption of the application, the computer-implemented methodcomprising: receiving, by a server, a first power nameplate for a firstapplication and a second power nameplate for a second application,wherein the first power nameplate identifies a first power consumptionlevel requirement of the first application, wherein the second powernameplate identifies a second power consumption level requirement of thesecond application, and wherein the second power consumption levelrequirement is a lower power consumption level requirement than thefirst power consumption level requirement; receiving, by the server, afirst priority rating of the first application and a second priorityrating of the second application, wherein the first priority rating is ahigher priority rating than the second priority rating; receiving, bythe server, a power descriptor from a mobile device, wherein the powerdescriptor identifies an amount of power available to the mobile devicefrom a battery on the mobile device; receiving, by the server, a set ofapplication downloading rules, wherein the set of applicationdownloading rules comprises a soft rule, a hard rule, and a medium rule,wherein the soft rule prioritizes downloading the first application overthe second application based on the higher priority rating of the firstapplication regardless of the higher power consumption level requirementof the first application, wherein the hard rule prioritizes downloadingthe second application over the first application based on the lowerpower consumption level requirement of the second application regardlessof the higher priority rating of the first application, and wherein themedium rule prioritizes downloading the second application over thefirst application in response to the amount of power available to themobile device from the battery being below a predetermined value;receiving, by the server, a request to upload the first application andthe second application to the mobile device; receiving, by the server, arule selection message, wherein the rule selection message selectivelychooses a selected rule from the soft rule, the hard rule, and themedium rule; and selectively uploading, from the server to the mobiledevice, the first application or the second application based on theselected rule.
 2. The computer-implemented method of claim 1, furthercomprising: receiving, by the server, a usage message, wherein the usagemessage describes a prediction of an amount of time during a predefinedtime period that the mobile device will be running the firstapplication; comparing, by the server, the amount of time during thepredefined time period that the mobile device will be running the firstapplication to a predetermined limit of time; and in response todetermining that the amount of time during the predefined time periodthat the mobile device will be running the first application is lessthan the predetermined limit of time, disregarding, by the server, thehard rule and uploading the first application to the mobile device. 3.The computer-implemented method of claim 1, further comprising:sampling, by the server, an average energy consumption by the mobiledevice for a predetermined sampling time interval; and selecting, by theserver, one of the hard rule, soft rule, and medium rule based on theaverage energy consumption by the mobile device for the predeterminedsampling time interval.
 4. The computer-implemented method of claim 1,wherein the selected rule is selected based on a priority leveldifference between the first priority rating and the second priorityrating.
 5. The computer-implemented method of claim 1, wherein the firstapplication is uploaded to the mobile device, and wherein thecomputer-implemented method further comprises: determining, by theserver, that usage of the first application on the mobile device exceedsa predetermined value; and in response to determining that usage of thefirst application on the mobile device exceeds the predetermined value,directing, by the server, the mobile device to remove the firstapplication from the mobile device and uploading, by the server, thesecond application to the mobile device.
 6. The computer-implementedmethod of claim 1, further comprising: determining, by the server, thatthe mobile device does not have sufficient battery power to operate anew application; and in response to determining that the mobile devicedoes not have sufficient battery power to operate the new application,removing, by the server, one or more existing applications on the mobiledevice and uploading the new application to the mobile device.
 7. Acomputer program product to control downloading of an application to amobile device based on power consumption of the application, thecomputer program product comprising a non-transitory computer readablestorage medium having program code embodied therewith, the program codereadable and executable by a processor to perform a method comprising:receiving a first power nameplate for a first application and a secondpower nameplate for a second application, wherein the first powernameplate identifies a first power consumption level requirement of thefirst application, wherein the second power nameplate identifies asecond power consumption level requirement of the second application,and wherein the second power consumption level requirement is a lowerpower consumption level requirement than the first power consumptionlevel requirement; receiving a first priority rating of the firstapplication and a second priority rating of the second application,wherein the first priority rating is a higher priority rating than thesecond priority rating; receiving a power descriptor from a mobiledevice, wherein the power descriptor identifies an amount of poweravailable to the mobile device from a battery on the mobile device;receiving a set of application downloading rules, wherein the set ofapplication downloading rules comprises a soft rule, a hard rule, and amedium rule, wherein the soft rule prioritizes downloading the firstapplication over the second application based on the higher priorityrating of the first application regardless of the higher powerconsumption level requirement of the first application, wherein the hardrule prioritizes downloading the second application over the firstapplication based on the lower power consumption level requirement ofthe second application regardless of the higher priority rating of thefirst application, and wherein the medium rule prioritizes downloadingthe second application over the first application in response to theamount of power available to the mobile device from the battery beingbelow a predetermined value; receiving a request to upload the firstapplication and the second application to the mobile device; receiving arule selection message, wherein the rule selection message selectivelychooses a selected rule from the soft rule, the hard rule, and themedium rule; and selectively uploading, to the mobile device, the firstapplication or the second application based on the selected rule.
 8. Thecomputer program product of claim 7, wherein the method furthercomprises: receiving a usage message, wherein the usage messagedescribes a prediction of an amount of time during a predefined timeperiod that the mobile device will be running the first application;comparing the amount of time during the predefined time period that themobile device will be running the first application to a predeterminedlimit of time; and in response to determining that the amount of timeduring the predefined time period that the mobile device will be runningthe first application is less than the predetermined limit of time,disregarding the hard rule and uploading the first application to themobile device.
 9. The computer program product of claim 7, wherein themethod further comprises: sampling an average energy consumption by themobile device for a predetermined sampling time interval; and selectingone of the hard rule, soft rule, and medium rule based on the averageenergy consumption by the mobile device for the predetermined samplingtime interval.
 10. The computer program product of claim 7, wherein theselected rule is selected based on a priority level difference betweenthe first priority rating and the second priority rating.
 11. Thecomputer program product of claim 7, wherein the first application isuploaded to the mobile device, and wherein the method further comprises:determining that usage of the first application on the mobile deviceexceeds a predetermined value; and in response to determining that usageof the first application on the mobile device exceeds the predeterminedvalue, directing the mobile device to remove the first application fromthe mobile device and uploading the second application to the mobiledevice.
 12. The computer program product of claim 7, wherein the methodfurther comprises: determining that the mobile device does not havesufficient battery power to operate a new application; and in responseto determining that the mobile device does not have sufficient batterypower to operate the new application, removing one or more existingapplications on the mobile device and uploading the new application tothe mobile device.
 13. A computer system comprising: a processor, acomputer readable memory, and a non-transitory computer readable storagemedium; first program instructions to receive a first power nameplatefor a first application and a second power nameplate for a secondapplication, wherein the first power nameplate identifies a first powerconsumption level requirement of the first application, wherein thesecond power nameplate identifies a second power consumption levelrequirement of the second application, and wherein the second powerconsumption level requirement is a lower power consumption levelrequirement than the first power consumption level requirement; secondprogram instructions to receive a first priority rating of the firstapplication and a second priority rating of the second application,wherein the first priority rating is a higher priority rating than thesecond priority rating; third program instructions to receive a powerdescriptor from a mobile device, wherein the power descriptor identifiesan amount of power available to the mobile device from a battery on themobile device; fourth program instructions to receive a set ofapplication downloading rules, wherein the set of applicationdownloading rules comprises a soft rule, a hard rule, and a medium rule,wherein the soft rule prioritizes downloading the first application overthe second application based on the higher priority rating of the firstapplication regardless of the higher power consumption level requirementof the first application, wherein the hard rule prioritizes downloadingthe second application over the first application based on the lowerpower consumption level requirement of the second application regardlessof the higher priority rating of the first application, and wherein themedium rule prioritizes downloading the second application over thefirst application in response to the amount of power available to themobile device from the battery being below a predetermined value; fifthprogram instructions to receive a request to upload the firstapplication and the second application to the mobile device; sixthprogram instructions to receive a rule selection message, wherein therule selection message selectively chooses a selected rule from the softrule, the hard rule, and the medium rule; and seventh programinstructions to selectively upload, to the mobile device, the firstapplication or the second application based on the selected rule; andwherein the first, second, third, fourth, fifth, sixth, and seventhprogram instructions are stored on the non-transitory computer readablestorage medium for execution by one or more processors via the computerreadable memory.
 14. The computer system of claim 13, furthercomprising: eighth program instructions to receive a usage message,wherein the usage message describes a prediction of an amount of timeduring a predefined time period that the mobile device will be runningthe first application; ninth program instructions to compare the amountof time during the predefined time period that the mobile device will berunning the first application to a predetermined limit of time; andtenth program instructions to, in response to determining that theamount of time during the predefined time period that the mobile devicewill be running the first application is less than the predeterminedlimit of time, disregard the hard rule and uploading the firstapplication to the mobile device; and wherein the eighth, ninth, andtenth program instructions are stored on the non-transitory computerreadable storage medium for execution by one or more processors via thecomputer readable memory.
 15. The computer system of claim 13, furthercomprising: eighth program instructions to sample an average energyconsumption by the mobile device for a predetermined sampling timeinterval; and ninth program instructions to select one of the hard rule,soft rule, and medium rule based on the average energy consumption bythe mobile device for the predetermined sampling time interval; andwherein the eighth and ninth program instructions are stored on thenon-transitory computer readable storage medium for execution by one ormore processors via the computer readable memory.
 16. The computersystem of claim 13, wherein the first application is uploaded to themobile device, and wherein the computer system further comprises: eighthprogram instructions to determine that usage of the first application onthe mobile device exceeds a predetermined value; and ninth programinstructions to, in response to determining that usage of the firstapplication on the mobile device exceeds the predetermined value, directthe mobile device to remove the first application from the mobile deviceand uploading the second application to the mobile device; and whereinthe eighth and ninth program instructions are stored on thenon-transitory computer readable storage medium for execution by one ormore processors via the computer readable memory.
 17. The computersystem of claim 13, further comprising: eighth program instructions fordetermining that the mobile device does not have sufficient batterypower to operate a new application; and ninth program instructions for,in response to determining that the mobile device does not havesufficient battery power to operate the new application, removing one ormore existing applications on the mobile device and uploading the newapplication to the mobile device; and wherein the eighth and ninthprogram instructions are stored on the non-transitory computer readablestorage medium for execution by one or more processors via the computerreadable memory.